Skip to main content

"does not exist in the current context" error in Visual Studio 2005

In ASP.NET development, there may be error "... does not exist in the current context" and the component ... lies obviously where it is. This may be a bug of Visual Studio 2005. When creating an aspx page, the component named "Label1" may be assigned a variable named "ctll00_Content1_Label1" in CLR, when the name "Label1" is changed, the name "ctll00_Content1_Label1" may not follow, and lead a error.


The solution of the problem is very simple. Just copy+X your code away, save the file, and then copy+V the code back for Visual Studio 2005 to perform refactoring of the code.

Comments

Popular posts from this blog

A simple implementation of DTW(Dynamic Time Warping) in C#/python

DTW(Dynamic Time Warping) is a very useful tools for time series analysis. This is a very simple (but not very efficient) c# implementation of DTW, the source code is available at  https://gist.github.com/1966342  . Use the program as below: double[] x = {9,3,1,5,1,2,0,1,0,2,2,8,1,7,0,6,4,4,5}; double[] y = {1,0,5,5,0,1,0,1,0,3,3,2,8,1,0,6,4,4,5}; SimpleDTW dtw = new SimpleDTW(x,y); dtw.calculateDTW(); The python implementation is available at  https://gist.github.com/3265694  . from python-dtw import Dtw import math dtw = Dtw([1, 2, 3, 4, 6], [1, 2, 3, 5],           distance_func=lambda x, y: math.fabs(x - y)) print dtw.calculate() #calculate the distance print dtw.get_path() #calculate the mapping path

Install mysql-python with mariadb

mysql-python requires libmysqlclient-dev in ubuntu, but the installation of mariadb will have the lib with unmet dependenccies, so the error of "mysql_config not found" may occurred if you install mysql-python via pip. The case is that mariadb has a compatible package, if you have the ppa setup as in  http://downloads.mariadb.org/ . Just "sudo apt-get install libmariadbclient-dev".

Config the size of shared memory(/dev/shm) for docker containers

Due to the issue from github , the size of shared memory is fixed at 64M. If you want larger size /dev/shm, please upgrade your docker to version newer than 1.10, and specify --shm-size when you run a docker image. Below is the help message of --shm-size. --shm-size="" Size of /dev/shm. The format is . number must be greater than 0. Unit is optional and can be b (bytes), k (kilobytes), m (megabytes), or g (gigabytes). If you omit the unit, the system uses bytes. If you omit the size entirely, the system uses 64m.